专利摘要:
A mobile terminal includes a display unit configured to display a home screen page having graphic objects corresponding to applications installed on the mobile terminal; and a controller (180) configured to execute a corresponding application in a background, control the corresponding application to be in a background enabled or disabled state, in response to a pre-set type of touch input applied on a graphic object of the corresponding application, when the corresponding application is in the deactivated state in the background, when receiving a request generated by the corresponding application for executing a function relating to the corresponding application, so as not to execute the function relating to the application, and when the corresponding application is in the activated state in the background, when receiving the request generated by the corresponding application for executing the function relative to the corresponding application, to execute the function relating to the corresponding application in the foreground.
公开号:FR3037164A1
申请号:FR1654847
申请日:2016-05-30
公开日:2016-12-09
发明作者:Kyongpil Tae；June Kim；Jeunguk Ha；Byul Jang
申请人:LG Electronics Inc；
IPC主号:

专利说明:

[0001] The present invention relates to a mobile terminal and, more particularly, to a mobile terminal capable of improving the energy efficiency by controlling the current consumption in a waking state, and an associated control method.
[0002] Terminals can generally be classified as mobile / portable terminals or fixed terminals. Mobile terminals can also be classified as portable terminals or on-board terminals. Mobile terminals have become more and more functional. Examples of these functions include voice and data communications, image and video capture via a camera, audio recording, music file playback via a speaker system, and display of audio. images and video on a screen. Some mobile devices have an additional feature that supports games, while other devices are configured as media players. More recently, mobile terminals have been configured to receive broadcast and multicast signals that allow viewing of content such as videos and television programs. As the mobile terminal becomes smaller and lighter for improved mobility, a battery in the mobile terminal also becomes smaller and lighter. However, as the battery becomes smaller and lighter, it has limited capacity. As a result, there is a need to use the limited capacity of the battery more efficiently. Recently, a method of breaking an application running on a background has been developed so that the capacity of the battery is controlled more efficiently. However, the method of the related art has the disadvantage of periodically interrupting the application which has been set to be automatically re-executed in the background. Therefore, one aspect of the detailed description is to provide a method of controlling applications running on a background. Another aspect of the detailed description is to provide an intuitive method of controlling the execution of an application on a background. Yet another aspect of the present invention relates to a method of reducing a standby current of a mobile terminal by controlling an execution state of an application on a background, even in an immortal service of the mobile terminal. application running in the background, for effective control of a limited capacity of a battery. In order to achieve these and other advantages and in accordance with objective 5 of this memo, as incorporated and extensively described herein, there is provided a mobile terminal, comprising: a display unit configured to display a display page; home screen comprising graphic objects corresponding to applications installed on the mobile terminal; and a controller configured to control the application to be in a background enabled state or a background disabled state, based on a pre-set type of touch input applied to the graphic object corresponding to the application. application, wherein the background enabled state of the application means an executable state of a function relating to the application, according to a request generated by the application for executing the function relating to the application, while the application is running on a background, and in which the background disabled state of the application means a restricted state of the application-related function, according to a request generated by the application for execution of the application function, while the application runs in the background. To achieve these and other advantages and in accordance with the objective 20 of this memo, as incorporated and extensively described herein, there is also proposed a method of controlling a mobile terminal, the method comprising: displaying a home screen page having graphic objects corresponding to applications installed on the mobile terminal; executing a power saving mode where a background activation state of the application is controlled, as requested by the user; and control the application so that the application is in a background activated state or a background disabled state in the power save mode, according to a preset type of touch input applied to the graphic object corresponding to the application and included in the home screen page, wherein the background enabled state of the application means an executable state of a function relating to the application, while the application is running on a background, and in which the background disabled state of the application means a restricted state of the application-related function, while the application is running backwards -plan.
[0003] An additional scope of applicability of the present application will be apparent from the detailed description given below. However, it should be understood that the description and the specific examples, while indicating preferred embodiments of the invention, are given by way of illustration only, since various changes and modifications to the spirit and The scope of the invention will be apparent to those skilled in the art from the detailed description. The accompanying drawings, which are included to provide a better understanding of the invention and are incorporated in and constitute a part of this specification, illustrate exemplary embodiments and together with the description serve to explain the principles of the invention. . In the drawings: Fig. 1 is a block diagram illustrating components of a mobile terminal according to an embodiment of the present invention; Figs. 2A and 2B are conceptual views illustrating application states in a general mode and a power saving mode, in a mobile terminal according to an embodiment of the present invention; Figures 2C and 2D are conceptual views illustrating a method of restricting the execution of application-related functions in a background disabled state of the applications; Fig. 3 is a flowchart illustrating a method of controlling a background activated state of an application in a power save mode in a mobile terminal according to an embodiment of the present invention; Figs. 4A to 4E are conceptual views illustrating a method of executing a power saving mode in a mobile terminal according to an embodiment of the present invention; Figs. 5A and 5B are conceptual views illustrating the control method of Fig. 3; Figs. 6A and 6B are conceptual views illustrating a method of selecting an application to be set to be in a background activated state in a power saving mode, in a mobile terminal in a mode of operation. embodiment of the present invention; Figs. 7A and 7B are conceptual views illustrating a method of setting an application to run in a background off state in a power saving mode, according to a preset condition; Figs. 8A and 8B are conceptual views illustrating a method of displaying a running state in the background of an application in a power saving mode; Figs. 9A to 9E are conceptual views illustrating a method of providing a home screen page in a power saving mode; and Figs. 10A-10C are conceptual views illustrating a method of executing applications in an energy saving mode. A description will now be given in detail according to exemplary embodiments disclosed herein, with reference to the accompanying drawings. For brevity of description with reference to the drawings, like or equivalent components may be provided with like or similar numerical references, and their description will not be repeated. In general, an addition such as "module" and "unit" can be used to designate elements or components. The use of this addition here is simply intended to facilitate the description of the brief, and the addition itself is not intended to give any meaning or special function. In the present disclosure, it is well known to those skilled in the art of the art that it has generally been omitted for brevity. The accompanying drawings are used to aid in easily understanding various technical features and it should be understood that the embodiments presented herein are not limited by the accompanying drawings. As such, the present disclosure should be construed as extending to all modifications, all equivalents and substitutes in addition to those set forth in particular in the accompanying drawings. The mobile terminals presented here can be implemented using different types of different terminals. Examples of these terminals include cell phones, smart phones, user equipment, laptops, digital broadcasting terminals, personal digital assistants (PDAs), portable media players (PMPs), browsers, laptops (PC), slate PCs, electronic tablets, ultra books, clothing devices (eg, smart watches, smart glasses, headphones (HMD)) and the like. By way of nonlimiting example only, a further description will be made with reference to particular types of mobile terminals. However, these teachings apply equally to other types of terminals, such as those types noted above. In addition, these teachings can also be applied to fixed terminals such as digital television, desktops, and the like. Reference is now made to FIG. 1, which is a block diagram of a mobile terminal in accordance with the present disclosure. The mobile terminal 100 is shown having components such as a wireless communication unit 110, an input unit 120, a detection unit 140, an output unit 150, an interface unit 160, a memory 170, a controller 180, and a power supply unit 190. The implementation of all of the illustrated components is not a necessary condition, and a larger or smaller number of components may alternatively be implemented. Referring now to Figure 1, the mobile terminal 100 is shown having a wireless communication unit 110 configured with a plurality of generally implemented components. For example, the wireless communication unit 110 typically includes one or more components that allow wireless communication between the mobile terminal 100 and a wireless communication system or network within which the mobile terminal is located. The wireless communication unit 110 typically includes one or more modules that enable communication such as wireless communications between the mobile terminal 100 and a wireless communication system, communications between the mobile terminal 100 and another mobile terminal. , communications between the mobile terminal 100 and an external server. In addition, the wireless communication unit 110 typically includes one or more modules that connect the mobile terminal 100 to one or more networks.
[0004] To facilitate these communications, the wireless communication unit 110 includes one or more of a broadcast receiving module 111, a mobile communication module 112, a wireless Internet module 113, a short-range communication module 114, and a position information module 115.
[0005] The input unit 120 includes a camera 121 for obtaining images or video, a microphone 122, which is a type of audio input device for inputting an audio signal, and a unit for user input 123 (for example, a touch key, a press key, a mechanical key, a function key, and the like) allowing a user to enter information. Data (eg, audio, video, images, and the like) is obtained by the input unit 120 and can be analyzed and processed by the controller 180 according to device parameters, user controls, and combinations thereof. The detection unit 140 is typically implemented using one or more sensors configured to detect internal information of the mobile terminal, the near-mobile environment, user information and the like. For example, in FIG. 1, the detection unit 140 is shown provided with a proximity sensor 141 and a lighting sensor 142. If desired, the detection unit 140 may alternatively or alternatively more include other types of sensors or devices, such as a touch sensor, an acceleration sensor, a magnetic sensor, a gravity sensor, a gyroscope sensor, a motion sensor, an RGB sensor, a sensor an infrared sensor (IR), a finger scan sensor, an ultrasonic sensor, an optical sensor (e.g., camera 121), a microphone 122, a battery charge indicator, an environmental sensor (e.g. a barometer, a hygrometer, a thermometer, a radiation detection sensor, a thermal sensor, and a gas sensor, among others), and a chemical sensor (e.g., an electronic nose, a health care sensor, a sensor biometric, and the like), just to name a few. The mobile terminal 100 may be configured to use information obtained by the detection unit 140, and in particular, information obtained by one or more sensors of the detection unit 140, and combinations thereof. Output unit 150 is typically configured to output various types of information, such as audio, video, touch output, and the like. The output unit 150 is shown having a display unit 151, an audio output module 152, a haptic module 153, and an optical output module 154. The display unit 151 may have an interlayer structure or integrated structure with a touch sensor to facilitate the use of a touch screen. The touch screen may provide an output interface between the mobile terminal 100 and a user, as well as operate as a user input unit 123 which provides an input interface between the mobile terminal 100 and the user.
[0006] The interface unit 160 serves as an interface with various types of external devices that can be coupled to the mobile terminal 100. The interface unit 160, for example, may include any one of wired or wireless ports. , external power supply ports, wired or wireless data ports, memory card ports, connection ports of a device having an identification module, input / output ports (E / S) audio, video I / O ports, earphone ports, and the like. In some cases, the mobile terminal 100 may perform various control functions corresponding to a connected external device, in response to the connection of the external device to the interface unit 160. The memory 170 is typically implemented to store data in order to To support various functions or features of the mobile terminal 100. For example, the memory 170 may be configured to store application programs executed in the mobile terminal 100, data or instructions for operations of the mobile terminal 100, and the like. Some of these application programs can be downloaded from an external server via wireless communication. Other application programs may be installed in the mobile terminal 100 at the time of manufacture or shipment, which is typically the case for basic functions of the mobile terminal 100 (for example, receiving a mobile terminal). call, placing a call, receiving a message, sending a message, and the like). It is common for application programs to be stored in the memory 170, installed in the mobile terminal 100, and executed by the controller 180 to perform an operation (or function) for the mobile terminal 100. The controller 180 typically operates to control a global operation of the mobile terminal 100, in addition to the operations corresponding to the application programs. The controller 180 can provide or process information or functions appropriate for a user by processing signals, data, information and the like, which are inputted or outputted by the various components mentioned above, or by activating the programs. In addition, the controller 180 can control at least one of the components mentioned above in FIG. 1, so as to control the application programs stored in the memory 170. furthermore, the controller 180 can operate at least two of the components of the mobile terminal 100 in a combined manner. The power supply unit 190 may be configured to receive an external power supply or provide an internal power supply to provide an appropriate power required to operate elements and components included in the mobile terminal 100. The power supply unit 190 may have a battery, and the battery can be configured to be integrated into the terminal body, or configured to be detachable from the terminal body. At least some of the above components may cooperatively operate to implement an operation or control method of a mobile terminal according to various embodiments which will be explained later.
[0007] The operation or the control method of the mobile terminal can be implemented on the mobile terminal by controlling at least one application program stored in the memory 170. Hereinafter, a control method of the mobile terminal will be explained in more detail. with reference to the accompanying drawings. The drawings will be explained in order according to the upper left drawing in a clockwise direction. In particular, FIGS. 2A and 2B are conceptual views illustrating application states in a general mode and a power saving mode, in a mobile terminal according to an embodiment of the present invention, and FIGS. 2D are conceptual views illustrating a method of restricting the execution of application-related functions in a background disabled state of the applications. The mobile terminal of the present invention can be executed in a general mode or a power saving mode. The general mode corresponds to a state of the mobile terminal where an application running in the background among one or more applications installed on the mobile terminal is not additionally controlled, in the same way as the related mobile terminal. More specifically, as shown in FIG. 2A, when the mobile terminal is executed in the general mode, the controller 180 can control an application to be in one of a disabled state, an enabled state, and a disabled state. a 3037164 9 state activated in the background. The deactivated state corresponds to an unloaded state of an application from the memory 170. The memory 170 may be a random access memory (RAM). In the deactivated state of the application, the application is not executed on a background and a foreground, and the execution of a function relating to the application is restricted. For example, when a message application is disabled, the mobile terminal can not receive messages from an external server or an external mobile terminal via network communication, since the execution of the network communication is restricted. . That is, in one embodiment of the present invention, when the message application is disabled, the mobile terminal can not receive messages from an external server or an external mobile terminal via network communication. in a state discharged from the memory 170. The context where the application is executed in the foreground corresponds to the one where an application execution screen is displayed on the display unit 151 as that the application is executed. The context where the application is running in the background corresponds to the one where the application is loaded on the memory 170, but is not yet executed in the foreground. In this case, the application is in a sleep state for execution in the foreground.
[0008] The activated state of the application corresponds to a state loaded with the application in the memory 170, and an executed state of the application in the foreground. In this case, the controller 180 may display an application execution screen on the display unit 151. The application may be executed in the background or in the foreground. More specifically, the application can be executed in the background or in the foreground according to a selection of the user. In other words, when a request to execute an application in the foreground is received, the controller 180 can execute the application in the foreground. For example, the controller 180 may execute the application in the foreground, in response to a touch input applied to a graphics object corresponding to the application.
[0009] If a request to display a screen other than an application execution screen is received while the application is running in the foreground, the controller 180 may interrupt the execution of the application by foreground, and run the application in the background. The request to display a screen other than an application execution screen may be a request to display a home screen page, or a request to display a screen. run screen of another application. For example, when the application run screen was displayed on the display unit 151 by running the application in the foreground, if a user request to display a home screen page is received, the controller 180 may display the home screen page on the display unit 151. The controller 180 may interrupt the execution of the application in the foreground, and can run the application in the background.
[0010] Controller 180 may automatically execute the application in the background without user request based on application setting information. The application setting information may be information set by a program developer of the application so that the application is automatically executed in the background when it is controlled by the program developer. In this case, even if the application is forcibly stopped according to a request from the user, if a predetermined time elapses, the controller 180 can automatically load the application on the memory 170 to execute the application backwards. plan. Such a setting is called an immortal service, a zombie service, and so on.
[0011] The immortal service can be used when continuous execution of the background application is required without user request. For example, a message application may use the immortal service, since the background will still need to be executed to receive a real-time message from an external server or external terminal. The application using the immortal service can be automatically re-executed in the background when a predetermined time elapses even if the application has been forcibly stopped by a user (i.e. if the application has been unloaded from the memory 170 after running the application in the background). In this case, even if the application using the immortal service is running in the background, a user of the mobile terminal can not recognize the execution state. The background enabled state is when an application loaded on the memory 170 is not executed in the foreground. In other words, the background enabled state is when an application is running in the background for quick execution of the application. Similarly, the background enabled state is a sleep state to wait for an application to run in the foreground. In this case, the controller 180 can directly execute an application in the foreground, without loading the application from the memory 170, since the application is in the background enabled state. In other words, the controller 180 can directly convert an application state to an activated state from the background enabled state, without loading the application onto the memory 170. In this case, the controller 180 can execute in the same state. foreground the application running in the background, faster than an application that is in a disabled state. Further, since the application running in the background is in a loaded state on the memory 170, a request to execute a function relating to the application may be generated by the application. If the application is running in the background (i.e., the application is in a background enabled state), the controller 180 may perform a function relating to the application, after the request. For example, when a message application is in a background enabled state, the mobile terminal may receive a message from an external server or an external terminal via network communication. Thus, a user of the mobile terminal can check in real time a message received from the external server or the external terminal. When the application is in the background enabled state, the controller 180 can not display an application execution screen on the display unit 151. In other words, since the activated state backwards The application map indicates a state of the application before execution, the application execution screen can not be displayed on the display unit 151. The energy saving mode corresponds to a state of the mobile terminal when an application running in the background is controlled, among one or more applications installed on the mobile terminal. More specifically, the power saving mode corresponds to a state of the mobile terminal when the execution of a function relating to an application running in the background is restricted. In other words, the power saving mode corresponds to a state of the mobile terminal where the consumption of a standby current is reduced when the execution of an application in the background is controlled. The standby current may be a current consumed in a sleep state where a specific application is not executed in the foreground. In other words, the standby current corresponds to a minimum current required to control the mobile terminal (i.e., required to maintain a mobile terminal power supply), and a current consumed by an application running in the background. mobile terminal. In the power save mode, an application can be set to be in one of a disabled state, an enabled state, a background enabled state, and a background disabled state. . In the power save mode, an application to be set to be in a disabled state in the background may be applicable to all the applications installed on the mobile terminal. Explanations about the disabled state, the activated state, and the background activated state will be replaced by the explanations mentioned above. In a manner other than the general mode mentioned above, in the power saving mode, an application running in the background may be set to be in a background enabled state or a background disabled state. . That is, in the power save mode, if an application is running in the background, the controller 180 can control the application to be in a background enabled state or a background disabled state. . Like the background enabled state, the background disabled state corresponds to the time when an application loaded on the memory 170 has not been executed in the foreground, i.e. Standby state to wait for execution in the foreground. However, the disabled state in the background is different from the background enabled state in the following manner. In the background disabled state, even if a request is generated by an application running in the background, the execution of a function relating to the application is restricted. For example, when a message application is in a background disabled state, even if a request to execute a network communication is received from the message application, the controller 180 can not execute the request. network communication. The controller 180 may restrict the receipt of a message from an external server or an external terminal via the network communication. In other words, a user of the mobile terminal does not receive a message when the message application is in the disabled state in the background.
[0012] 3037164 13 In the power save mode, the background disabled state and the background enabled state are not related to whether an application is running in the background or not. In other words, the setting of an application in the background off state in the power saving mode corresponds to the setting where an application to be executed in the background is controlled in the disabled state in the background. In one embodiment of the present invention, setting an application in the background off state in the power saving mode does not mean that the application is running in the background. Similarly, the setting of an application in the background enabled state corresponds to the setting where an application running in the background is checked in the background enabled state. In other words, in the power saving mode, setting an application in the background enabled state does not mean running the application in the background.
[0013] Hereinafter, a method of restricting execution of a function relating to an application, when the application is running in the background in the background disabled state, will be explained in more detail. Referring to Fig. 2C, the controller 180 may receive a request for execution of an application-related function from the background application (S210).
[0014] The application running in the background has been loaded on the memory 170, and generates a request to execute a function relating thereto. On the other hand, when the application is in a disabled state, i.e., when the application has not been loaded into the memory 170, the application can not generate a request for execution of the application. a function relating to it. An application running in the foreground generates a request to execute a function relating to the application, and can execute the application. In other words, the control method according to one embodiment of the present invention is not applicable to an application that is in a disabled state, or to an application that is running in the foreground in an activated state.
[0015] Once a request to execute a function relating to the application is received, the controller 180 can determine whether the application is in a background enabled state or not (S220). When the application is in a background enabled state (Yes at S220), the controller 180 may perform a function relating to the application (S230). If the application is in a background enabled state, the controller 180 may transmit a request for execution of a function relating to the application, to the function relating to the application, so that the function relating to the application is executed. In this case, the controller 180 can perform the function 5 relating to the application in the background. In other words, the controller 180 can load the application function from the memory 170, and perform the function relating to the application in the background. In this case, the application function may be a function to perform data communication with the application. For example, when the application is a message application and a function relating to the application is a network function, if a request to execute the network function is received from the message application, the controller 180 can transmit the request to the network function so that the network function is executed. In addition, if a control command is transmitted by the network function, the controller 180 may transmit the control command to the message application. Upon completion of the execution of the application function, the controller 180 may interrupt the execution of the application function, or control the function to run continuously back and forth. plan. In other words, when the execution of the application function is completed, the controller 180 may unload the application-related function from the memory 170, or control the function for continuous execution. in the background to wait for the execution in the foreground. In contrast, if the application is in a background disabled state, the controller 180 restricts execution of the application-related function, thereby denying execution of the application-related function (S240) . If it is determined that the application is in a background disabled state, the controller 180 can not transmit a request to execute the function relating to the application, the application function, the so that the function relating to the application is not executed. In other words, in one embodiment of the present invention, the application does not perform data communication with the application-related function.
[0016] More specifically, with reference to Fig. 2D, while an application (app A) is running in the background in a background disabled state, the controller 180 may receive a request to execute a request. function (service A) relating to the application. In this case, the controller 180 can not transmit a request to execute the function (service A) relating to the application, to the function (service A) relating to the application, so that the function (service A) relative to the application is not executed. The controller 180 may further include a service manager 1800 configured to determine whether to execute the application-related function in a background running state of an application. Hereinafter, it is assumed that the controller 180 controls an application running in the background. However, the service manager 1800, and not the controller 180, controls an application running in the background. The application-related function (service A) may be a function performed in conjunction with a function provided by an application when the application is in a background-enabled state. For example, when the application is a message application, the application-related function may be a network communication function, an SNS function, a message application, and so on. The function relating to the application can be pre-stored in the memory 170.
[0017] For example, the memory 170 may further include a look-up table 1700 for storing functions relating to applications whose execution is restricted, in a background deactivated state. Correspondence table 1700 can store mapping information between applications and application-related functions, functions whose execution is restricted in a background disabled state of the applications. The controller 180 can determine whether to transmit a request for execution of a function (service A) relating to an application (app A) to the function (service A) relating to the application, according to the information stored in the correspondence table 1700. The controller 180 can not transmit a request for execution of the function (service A) relating to the application, to the function (service A) when the application is stored in the table correspondence 1700.
[0018] In other words, in one embodiment of the present invention, when an application is in a disabled state in the background, a request to execute a function relating to the application is not transmitted to the application. application function. Communication between the application and the application-related function can be controlled so that the application-related function is not executed. When a request for execution of the function (service A) relating to the application (app A) is not transmitted, the controller 180 can transmit to the application a feedback signal indicating that the execution of the function relative to the application has been restricted. Unlike an application disabled state, the background disabled state is when an application has been loaded into memory 170. Thus, in the background disabled state, the application can be executed quickly. More specifically, when an application is in a background disabled state, the controller 180 may directly execute the application, without loading the application into the memory 170, in response to receiving a request for execution of the application. In contrast, when an application is in a disabled state, the controller 180 can execute the application after the application is loaded from the memory 170, in response to receiving a request to execute the application. application. In other words, in one embodiment of the present invention, a standby current can be reduced by restricting the performance of additional functions in the background, while a loaded state of an application in the memory 170 is maintained. Further, in one embodiment of the present invention, since a state loaded with an application in the memory 170 is maintained, the application is executed directly in the foreground, without being loaded from the memory 170 This can reduce the current consumption for loading the application from memory 170. The above description describes an executed state of an application in a general mode and a power saving mode. and a method of controlling an application in a disabled state. Hereinafter, a method of controlling an executed state of an application in an energy saving mode will be explained in more detail.
[0019] FIG. 3 is a flowchart illustrating a method of controlling a background activated state of an application in a power saving mode in a mobile terminal according to an embodiment of the present invention, FIGS. 4A. 4E are conceptual views illustrating a method of performing a power saving mode in a mobile terminal according to an embodiment of the present invention, and FIGS. 5A and 5B are conceptual views illustrating the control method. of Fig. 3. First, the mobile terminal according to one embodiment of the present invention executes a power saving mode (S310). The controller 180 of the mobile terminal can execute a power saving mode while a general mode is executed, according to a selection of the user or a preset condition. In other words, the mobile terminal of the present invention can be operated in a general mode unless additional control is achieved. The mobile terminal can execute a power saving mode according to a user selection or a preset condition. When the mobile terminal executes a power saving mode according to a selection of the user, the controller 180 may receive a request to execute a power saving mode from a user. For example, as shown in FIG. 4A, the request to execute a power saving mode can be received via a status display window. The status display window may be a page for displaying status information of the mobile terminal on the display unit 151. The mobile terminal status information includes information relating to terminal operation. such as a display unit brightness 151, notification information generated from at least one application installed on the mobile terminal, a network state of the mobile terminal, and a sensor state of the mobile terminal. mobile terminal. The status display window may be displayed on the display unit 151 when a preset touch type is applied to a specific position of the display unit 151. For example, as shown in FIG. In the first drawing of Figure 4A, the controller 180 may display the status display window based on a slip input from one end of the display unit 151.
[0020] The status display window may further comprise a graphic object 600 for converting an operating state of the mobile terminal. For example, as shown in a second drawing of FIG. 4A, the status display window may further comprise a graphic object 600a relating to the execution of a power saving mode, a relative graphic object 600b. a state conversion of a mobile terminal network, a graphic object 600c relating to a state conversion of a short-range communication, and a graphic object 600d relating to an LTE communication state conversion. The controller 180 may execute a power saving mode when the graphics object 600a relating to the execution of a power saving mode is touched. As shown in a third drawing of Figure 4A, the controller 180 can display energy saving mode information on the display unit 151, so that a user recognizes functions in the power save mode. . Once the power saving mode is executed, the controller 180 can set the remaining applications to be in a disabled state in the background, with the remaining applications except for one or more applications tuned for be in a background activated state among a plurality of applications installed on the mobile terminal. Applications to be executed in a background enabled state in an energy saving mode may be selected by one of the plurality of applications installed on the mobile terminal. For example, the controller 180 can set a telephone signal for sending / receiving a call signal, a transmission / reception message application for a message, and a notes application, so that they are in a state enabled in the background.
[0021] In the power save mode, a function that should be performed in the background of the mobile terminal (for example, a telephone function for transmitting / receiving a call signal, etc.) can always be set to be in a state enabled in the background. In this case, the function that should be running in the background of the mobile terminal may not be able to be set to be in the off state in the background. Once the power saving mode is executed, the controller 180 can provide the same home screen page as in a general mode. In other words, in one embodiment of the present invention, the executable applications in a power-saving mode are not restricted, but only a background execution state is controlled. Thus, the same home screen page as in a general mode can be provided. In one embodiment of the present invention, since the same home screen page is provided in a general mode and a power save mode, a user can provide the power save mode without further adjusting a home screen page relating to the energy saving mode. In addition, in one embodiment of the present invention, a user can access all functions installed on the mobile terminal even in a power saving mode. In other words, a user can run all the applications installed on the mobile terminal, even in a power saving mode. For example, the controller 180 may execute an application set to be in a background disabled state, in response to receiving an execution request from the application set to be in a background disabled state.
[0022] The controller 180 can change an aspect of a graphic object included in the home screen page, according to a background activation state. For example, as shown in a fourth drawing of Figure 4A, the controller 180 may output a graphical object 300 corresponding to a note application that is in a background activated state, and a graphical object 310 corresponding to a SNS application which is in a deactivated state in the background, with a different brightness, so that the graphic objects 300, 310 visually differ from each other. Thus, a user can intuitively recognize an application that is in a disabled state in the background, and an application that is one in a background enabled state.
[0023] As another example, the controller 180 may execute a power saving mode by using a function to change a setting of the mobile terminal. The function for changing a mobile terminal setting can be changed to various terms such as 'environment setting' and 'setting'. The change of setting function of the mobile terminal may be a setting change function relating to operation of the mobile terminal, such as a communication connection state, an output state, and an input state of the mobile terminal. . In this case, a user can execute a power saving mode by executing the change of setting function of the mobile terminal.
[0024] If the power saving mode is executed according to a preset condition, the controller 180 may execute the power save mode according to the preset condition, or output notification information for execution of a mode. energy saving. The preset condition can be set directly by a user, or can be set when the mobile terminal is introduced to the market. The preset condition may be one of a condition relating to a position of the mobile terminal, a condition relating to a time, a condition relating to a remaining quantity of a battery, and a condition relating to a usage pattern. 'an application. Alternatively, the preset condition may be a condition implemented when at least two of the condition relating to a time, the condition relating to a remaining quantity of a battery, and the condition relating to a usage scheme of a application are combined with each other. More specifically, the positional condition of the mobile terminal may be a condition that a current position of the mobile terminal corresponds to a specific position, a condition that a current position of the mobile terminal corresponds to a position rather than a position. pre-stored, or a condition relating to a path of the mobile terminal. The condition relating to a time may be a condition that a current time corresponds to a preset period. The condition relating to a remaining amount of a battery 20 may be a condition that a remaining amount of a battery is less than a preset amount. The condition relating to a schema of use of an application may be a condition relating to an application execution frequency, a frequent execution time, an executed state, etc. The preset condition may be a condition that the path information generated as positional information interoperating with time does not correspond to a preset path. For example, as shown in Figure 4B, if it is detected that a current position of the mobile terminal corresponds to a position `13 'different from a preset position' A ', the controller 180 may display notification information for The preset position can be stored by a user or by the controller 180. When the preset position is stored by the controller 180, the preset position can be stored by the user or the controller 180. The preset position can be stored by the controller 180. be a position detected by a mobile terminal position detection module, which may be a position of a home or company. In this case, if a position rather than the preset position is detected, the controller 180 may recommend a power saving mode to save the battery. In other words, in one embodiment of the present invention, if a user is located at a position where a loading operation can not be performed easily, a power saving mode is implemented so that a risk of discharge of energy is avoided. a battery can be reduced. The notification information may be outputted as an intruder window 400. The intruder window 400 may include information relating to a power saving mode, a graphics object 410 for executing a power saving mode. , and a graphic object 420 for non-execution of a power saving mode. If the graphics object 410 for executing a power save mode is selected, the controller 180 may execute a power saving mode. In addition, if the graphic object 420 for non-execution of a power saving mode is selected, the controller 180 can maintain a general mode without executing a power saving mode. As another example, the controller 180 may output notification information for execution of a power save mode, based on a position of the mobile terminal and a remaining amount of a battery. For example, if a current position of the mobile terminal corresponds to 'B' different from the pre-stored position 'A' and a remaining amount of a battery is less than a preset amount, the controller 180 may display notification information for executing a power saving mode, on the display unit 151.
[0025] Once the preset condition is satisfied, the controller 180 can directly execute a power save mode without outputting notification information. For example, as shown in FIG. 4C, if a current position of the mobile terminal corresponds to 'B' different from the pre-stored position 'A', the controller 180 can directly execute a power saving mode. While the power saving mode is running, the controller 180 can unblock the power saving mode and convert the power saving mode to a general mode, according to a user request or when a preset condition is set. is satisfied. For example, as shown in FIG. 4D, if a touch input is applied to the graphic object 600a relating to execution of a power saving mode and included in the state display window, while the mode Energy saving is executed, the controller 180 can unlock the energy saving mode and can convert the power saving mode to a general mode. As another example, if it is detected that a current position of the mobile terminal corresponds to the pre-stored position 'A' while the energy saving mode is running, the controller 180 can output notification information to a user so as to recommend an unlocked state of the energy saving mode. In this case, the controller 180 can determine that the power save mode is no longer needed, and may prompt the user to convert the power saving mode to a general mode via notification information. For example, as shown in a second drawing of FIG. 4E, if the pre-stored position 'A' is detected while the energy saving mode is running, the controller 180 can output an intruder window including notification information. recommending an unlocked state of the power saving mode. In this case, the notification information may comprise a graphic object indicating a 'power save mode enable' function to unblock a power saving mode and convert it to a general mode, and a graphical object indicating a 'Subsequent Notification' function to maintain a current energy saving mode and provide further notification information. When executing the power saving mode, the mobile terminal can display graphic objects corresponding to applications installed on the mobile terminal, on a home screen page, in the power saving mode (S320 ). Once the power save mode is executed, the controller 180 can set the remaining applications to be in a disabled state in the background, with the remaining applications except for one or more applications set to be disabled. in a background activated state among a plurality of applications installed on the mobile terminal. A home screen page, which includes one or more graphical objects relating to one or more applications set to be in a background enabled state, and one or more graphical objects relating to one or more applications configured for in a background disabled state among a plurality of applications installed on the mobile terminal, may be displayed on the display unit 151. The home screen page may represent displayed screen information on the display unit 151 in a standby state of the mobile terminal. The home screen page can also be called a screen saver, menu screen, home screen, and so on. More specifically, the home screen page may represent screen information displayed when the mobile terminal is turned on, or may represent screen information including graphic objects relating to functions of the mobile terminal such that functions are executable. The home screen page has a size corresponding to the display unit 151, and may be provided in plurality in number according to a user setting. Referring to FIG. 5, the home screen page may include at least one of a status display region 210, an information display region 220, and a base region 230. The status display region 210 may be a region where information relating to an operating state of the mobile terminal is displayed. For example, the status display region 210 may include information about a communication state of the mobile terminal, information about a current time, information about a remaining amount of a battery, information about an activated state. a sensor, etc. The information display region 220 may be a region where at least one graphic object corresponding to at least one executable function in the mobile terminal is displayed. The at least one graphic object corresponding to at least one executable function in the mobile terminal may include an application icon and a computer gadget. The icon may correspond to an execution function of an application. The computer gadget can represent simple information of an application, or can be an application program for displaying a run screen on a home screen page. The information display region 220 may include graphics objects 200a, 200b, 200c corresponding to a shortcut function for entering directly into each home screen page where a plurality of screen pages are located. Home. The graphic objects 200a, 200b, 200c corresponding to a shortcut function can be formed so that the graphic object 200a corresponding to a home screen page currently outputted to the display unit 151 has a different appearance (e.g., color, shape, size, etc.) of the graphic objects 200b, 200c corresponding to home screen pages that are not outputted to the display unit 151, so that a user recognizes the home screen page currently output to the display unit 151. The base region 230 may be a region selected by a user, or a region where icons relating to applications Presets are displayed when the handheld is introduced to the market. The base region 230 may be a common region of the plurality of home screen pages. In other words, the base region 230 can still be displayed even if the plurality of home screen pages are switched. The base region 230 may include applications that are always provided even if the plurality of home screen pages are switched. For example, the base region 230 may include a telephone application, a message application, and so on. The base region 230 may provide an application that is in a background activated state in a power saving mode. In other words, an application that is in a background enabled state may still be provided on the base region 230 in a power saving mode. If there is a plurality of home screen pages, one of the plurality of home screen pages may be displayed on the display unit 151. When one of the plurality of home screen pages is present, Home screen pages have been displayed on the display unit 151, if a preset touch type is applied to the display unit 151, the controller 180 can change the information display region 220 displayed on said home screen page, in an information display area displayed on another home screen page. The home screen page can be generated according to a user setting, or according to a preset condition. For example, if the mobile terminal enters a power saving mode, controller 180 may generate a new home screen page with only graphical objects corresponding to applications that are in a background activated state. in the energy saving mode. Even if the power saving mode is executed according to a request to execute the energy saving mode, the controller 180 can provide the same home screen page as in a general mode. This can resolve a user's discomfort when switching between home screen pages when a general mode is converted to a power saving mode. When executing the power saving mode, the controller 180 may control the display unit 151 to have a lower brightness than in a general mode. This can reduce power consumption due to brightness of the display unit 151. In addition, even in the power saving mode, the controller 180 can execute a plurality of applications installed on the mobile terminal in advance. plan. In other words, in the power save mode, the execution of at least one of a plurality of applications installed on the mobile terminal in the foreground is not restricted. Thus, in one embodiment of the In the present invention, a user can access all applications. The plurality of applications may be preinstalled on the mobile terminal memory 170 when the mobile terminal is commercially available, or may be installed on the memory 170 after being downloaded from an external server (for example, Google Play), Android Market, an application store (app), etc., via a network, according to a selection of the user. The mobile terminal according to one embodiment of the present invention can determine a background activation state of the applications, according to a pre-set type of touch input applied to application-related graphics objects, when Home screen has been displayed on the display unit 151 in the power saving mode (S330). The controller 180 can perform different application-related functions when different types of touch input are applied to the graphics objects included in the home screen page. The different types of touch inputs may include various types of touch inputs such as a short touch, a long touch, a multiple touch, a slip touch, and a double touch. The application-related functions may include an application execution function in the foreground, a function of changing an application display position on the home screen page, a function of deleting the application of the memory 170, a function of changing an application size, a function of determining a state activated in the background of the application, etc. For example, if a short touch is applied to the graphic object included in the home screen page, the controller 180 can execute the application in the foreground. As another example, if a long touch is applied to the graphic object included in the home screen page, the controller 5 can change a background enabled state of the application. In other words, in one embodiment of the present invention, in a power save mode, a background enabled state of the application may be changed on the home screen page in a different manner. compared to a general mode. Thus, in one embodiment of the present invention, a background running state of the application can be monitored on the home screen page in the power save mode without the terminal mobile enters an additional screen. This can provide an intuitive interface to a user. A method of changing the execution state in the background of the application will be explained in more detail. The controller 180 can detect a pre-set type of touch input applied to a graphics object corresponding to the application, in the power save mode. The preset touch type can have various types of touch inputs such as a long touch, a multiple touch, and a double touch. The controller 180 can determine an activation state in the background of the application. More specifically, when the application has been set to be in a background enabled state, the controller 180 can change the state of the application to a disabled state in the background, depending on the type of touch. preset. In addition, when the application has been set to be in a background disabled state, the controller 180 can change the state of the application to a background enabled state, depending on the type of application. pre-set touch. For example, as shown in a first drawing of FIG. 5A, the controller 180 may display a home screen page including the graphic object 300 corresponding to a notes application, and the graphic object 310 corresponding to a graphics application. Social Networking Service (SNS), in a 30 energy saving mode. The SNS application corresponds to an application for providing an information sharing service when a plurality of users subscribe to a single server.
[0026] The controller 180 may determine a background enabled state of the notes application in response to a long touch input applied to the graphical object 300 corresponding to the notes application. For example, when the notes application has been set to be in a background disabled state, the controller 5 can change the state of the notes application to a background enabled state. If the state of the notes application is changed to the background enabled state of the off state in the background, the controller 180 can change an appearance of the graphical object 300 corresponding to the notes application. For example, as shown in a second drawing of FIG. 5A, the controller 180 can change a color of the graphical object 300 corresponding to the notes application to a more vivid color than a gray, a darker color than in the activated state in the background. As a further example, as shown in the first and second drawings of FIG. 5B, when the notes application has been set to be in a background disabled state, the controller 180 can change the state of the display. application notes in a state activated in the background, in response to a long tactile input applied to the graphic object 300 corresponding to the notes application. In this case, as shown in a third drawing of Figure 5B, the controller 180 can change the state of the notes application to a disabled state in the background, in response to a long touch input applied to the graphic object. 300 and may change a color of the graphic object 300 corresponding to the notes application to a darker color than in the background enabled state. With such a configuration, a user can easily change a background activation state of each application on each home screen page. In addition, the user can intuitively recognize an activation state in the background of each application on each home screen page. In the power saving mode, the controller 180 may control an application in a different manner, depending on whether the application is in the background enabled state or the background disabled state. More specifically, when the application is running in the background, the controller 180 may control the application to be in a background enabled state or a background disabled state. In other words, when the application has been set to be in a background enabled state, the controller 180 can execute communication between the application and a function relating to the application, so that the relative function 3037164 28 to the application is executable in the background when the application is running in the background. In contrast, when the application has been set to be in a background disabled state, the controller 180 can not execute communication between the application and an application-related function when the application is executed in the background. background. For example, if a foreground execution request from an application that has been set to be in a background enabled state is received, the controller 180 may execute the application in the foreground in the same manner than a general mode. Similarly, if a foreground request for an application that has been set to be in a background disabled state is received, the controller 180 may execute the application in the foreground. Once the application is executed in the foreground, the controller 180 can unblock a restricted state of execution of applications that have been set so that they can not be executed in a background disabled state.
[0027] In this case, if the application running in the foreground is running in the background, the controller 180 can control the application to be in a background enabled state or a background disabled state. . In other words, when the application has been set to be in a background disabled state, if the application is run in the background again, the controller 180 may restrict a function relating to the application and executable in the background. foreground. In contrast, when the application has been set to be in a background enabled state, if the application is run in the background again, the controller 180 may continuously perform a function relating to the application, the function that has been executed in the foreground. Heretofore, a method of determining a background activation state of each application in an energy saving mode has been explained. Hereinafter, a method of selecting an application to be set to be in a background activated state in an energy saving mode will be explained in more detail. In particular, Figs. 6A and 6B are conceptual views illustrating a method of selecting an application to be set to be in a background activated state in a power saving mode, in a mobile terminal according to an embodiment of the present invention. Once a power saving mode is executed, the controller 180 may set a plurality of applications installed on the mobile terminal to be in a background enabled state or a disabled back state. -plan. A user can select an application to set to be in a background enabled state in the power save mode. In this case, an application that has not been selected by the user can be set to be in a disabled state in the background in the power saving mode. As mentioned above, the controller 180 may select an application to be set to be in a background enabled state in the power save mode, by applying a preset type of touch input to a corresponding graphics object. to 10 the application on the home screen page. In addition, the controller 180 may select an application to be set to be in a background enabled state in the power saving mode, using a list of a plurality of applications installed on the mobile terminal. For example, as shown in a first drawing of FIG. 6A, the controller 180 may execute a power saving mode according to a request from the user. As shown in a second drawing of Fig. 6A, once the power saving mode is executed, the controller 180 may display on the display unit 151 a list of applications 610 of a plurality of applications installed on the mobile terminal, so that a user selects an application to be set to be in a background activated state in the power saving mode. The application list 610 can be displayed only when a power save mode is first executed, or can be displayed each time the power saving mode is executed. If the list of applications 610 is displayed, the controller 180 can select at least one of the plurality of applications included in the application list 610 according to a selection of the user. For example, as shown in a second drawing of Figure 6A, the controller 180 may select a note application. Then, the controller 180 can set at least one user selected application to be in a background enabled state, and adjust the remaining applications to be in a background disabled state. For example, as shown in a third drawing of Figure 6A, the controller 30 can adjust the remaining applications other than the notes application to be in a disabled state in the background. After the application has been set to be in a background enabled state in the power saving mode, the controller 180 can change (add or delete) the application to be set to be in a state. activated in the background, according to a request from the user. For example, as shown in a first drawing of Figure 6B, the mobile terminal may be in a power saving mode where only a note application is set to be in a background enabled state, and the remaining applications are set to be in a disabled state in the background.
[0028] The controller 180 may output the status display window according to a touch input preset type applied to a preset region of the display unit 151 (e.g., the display region of the display unit). state 210). As mentioned above, the status display window may include the graphic object 600 relating to status information of the mobile terminal and change the status information.
[0029] The status display window may further include time information 700 indicating a remaining time (usable time) of the mobile terminal in a remaining amount of a battery, in a power saving mode. The remaining time of the mobile terminal can be calculated from a current remaining amount of a battery, and a user's average current consumption amount. For example, as shown in a second drawing of FIG. 6B, the time information 700, indicating that the mobile terminal can be used for 17 days in an energy saving mode according to a current remaining amount of a battery , can be displayed on the status display window. The controller 180 may perform different functions relating to a power saving mode on the status display window, according to different types of touch inputs applied to the graphic object 600a relating to the execution of the display. 'an energy saving mode. More specifically, if a short touch is applied to the graphical object 600a relating to the execution of a power save mode, the controller 180 may execute a power save mode, or may unlock the power saving mode. energy executed. For example, if a short touch is applied to the graphical object 600a relating to the execution of a power saving mode, during a power saving mode, the controller 180 can unlock the executed state of the economy mode. energy and can execute a general mode. If a short touch 3037164 31 is applied to the graphic object 600a relating to the execution of a power saving mode, during a general mode, the controller 180 can unlock the run state of the general mode and can execute a mode energy saving. The graphic object 600a relating to the execution of a power saving mode 5 can be displayed in a different color, according to a mode executed from the mobile terminal. For example, when the mobile terminal is in an energy saving mode, the graphic object 600a may be displayed in green. In addition, when the mobile terminal is in a general mode, the graphic object 600a may be displayed in gray.
[0030] As shown in a second drawing of Figure 6B, the controller 180 can add or remove an application to be set to be in a background enabled state in the power save mode, based on a touch input. long applied to the graphic object 600a relating to the execution of a power saving mode. For example, the controller 180 may display a list of applications including a plurality of applications installed on the mobile terminal, on the display unit 151, as an intruder window 620, based on a touch input. long applied to the graphic object 600a relating to the execution of a power saving mode. The intruder window 620 may include the application information 620a for an application set to be in a background activated state in a power saving mode, and application information 620b for a plurality of applications installed on the mobile terminal. The controller 180 can set at least one application to be in a background activated state, among a plurality of applications installed on the mobile terminal, according to a selection of the user. In addition, the controller 180 can unblock the set state of the at least one application, according to a selection of the user. For example, as shown in a third drawing of Figure 6B, the controller 180 may add a telephone application as a set application to be in a background enabled state. In this case, as shown in a fourth drawing of FIG. 6B, the controller 180 may display the graphical object 300 corresponding to the notes application, and the graphical object 310 corresponding to the SNS application, so as to visually distinguish the remaining applications. For example, the controller 180 may display the graphical object 300 corresponding to the notes application and the graphical object 310 corresponding to the SNS application in a bright color, while the controller 180 may display the remaining applications in a random color. dark color. The above description describes a method of selecting an application to be set to be in a background enabled state in a power saving mode by a user. Hereinafter, an automatic selection method of an application to be set to be in a background activated state in an energy saving mode will be explained. The controller 180 of the mobile terminal according to one embodiment of the present invention can detect an application to be set to be in a background activated state in a power saving mode, according to a preset condition. In other words, in a power saving mode, an application that has not been set to be in a background enabled state can be in a background disabled state. The preset condition may be a condition relating to at least one of an application usage pattern, a remaining amount of a battery, a power hold time, an application recently used, and an amount of power consumption of an application. More specifically, as shown in a first drawing of Fig. 7A, when a user enters a supply hold time, the controller 180 can detect a consumable amount of current per hour, based on the dwell time of power supply and a remaining time of a battery. Then, the controller 180 can detect at least one application, based on the amount of consumable current per hour, and a current consumption amount of each of a plurality of applications installed on the mobile terminal.
[0031] For example, if the amount of consumable current per hour is 60 ma / hr, the controller 180 can detect applications having a current consumption amount of 60 ma / hr or less. Then, the controller 180 can set the detected applications as applications for use in a power saving mode. As shown in a second drawing of Figure 7A, the controller 180 may display notification information including information about the detected applications on the display unit 151. For example, the detected applications may be a message application. 720 and a call application 710. The notification information may further comprise a graphic object 3037164 33 to select whether to run a power saving mode or not. For example, as shown in a second drawing of Figure 7A, the notification information may further include a graphic object corresponding to a "power save mode execution" function to execute a power saving mode, and a graphic object corresponding to a "subsequent notification" function for providing notification information later without executing a power saving mode. Once the energy saving mode run function is selected, the controller 180 may execute a power saving mode where the detected applications are set to be in a background enabled state, and the applications remaining are set to be in a disabled state in the background. Once the subsequent notification function is selected, the controller 180 may continuously run a general mode without executing a power saving mode. As a further example, the controller 180 can detect an application to be set to be in a background enabled state in a power saving mode, according to an application usage scheme by a user. . The application usage pattern may include at least one of an application execution frequency (number of times), an application execution time, and a recently used application.
[0032] For example, as shown in FIG. 7B, when a weather application 320 for providing meteorological information, and an alarm application 330 for outputting an alarm are executed frequently between 9:00 and 12:00, the controller 180 can set weather app 320 and alarm application 330 to be in a background enabled state. At the same time, the controller 180 can adjust the remaining applications installed on the mobile terminal (for example, a notes application, a directory application for providing contact information, a browser application, etc.) for in a disabled state in the background, between 9:00 am and noon.
[0033] If a note application is frequently used between noon and 3:00 pm, the controller 180 may set the note application to be in a background enabled state and may adjust the remaining applications installed on the mobile terminal (for example, example, a weather application, an alarm application, etc.) for 3037164 34 they are in a disabled state in the background, between noon and 15:00. In this case, on the display unit 151, the graphic object 300 corresponding to the notes application can be displayed to indicate a state activated in the background, and graphic objects 320, 330 relating to the remaining applications. can be displayed 5 to indicate a disabled state in the background. As a further example, if a request to execute a power saving mode is received, the controller 180 can detect a recently used application before executing a power saving mode. The recently used application may be an application that has been executed at a time close to a run time of a power saving mode. The recently used application may be a predetermined number of applications that have been most recently executed based on a run time of a power saving mode. Alternatively, the recently used application may be an application that has been run for a preset period of time based on a run time of a power save mode. Once a power saving mode is executed, the controller 180 can set the recently used application to be in a background enabled state, and can adjust the remaining applications to be in a state disabled in the background. The above description describes a method of setting an activated state in the background of an application according to a preset condition. In one embodiment of the present invention, the consumption of a standby current occurring when an unnecessary application is activated in the background may be reduced. Hereinafter, a method of displaying a running state in the background of an application in an energy saving mode will be explained. In particular, Figs. 8A and 8B are conceptual views illustrating a method of displaying a running state in the background of an application in a power saving mode. Once a power save mode is executed, at least one of a plurality of applications installed on the mobile terminal can be set to be in a background enabled state, and the remaining applications can be set. to be in a disabled state in the background. In this case, a user can not recognize which application is running in the background on the home screen page, or can not recognize that an application is in a 3037164 state enabled in the background or in a state disabled in the background. In other words, when an application is running in the background, a user can not recognize a state of the application running in the background, since an execution state of the application is not output. to the display unit 151.
[0034] Thus, in one embodiment of the present invention, in a power saving mode, a type of output (or visual appearance or output form) of a graphic object corresponding to an application included in a screen page. host can be determined from an activation state in the background of the application. The output type of the graphic object corresponds to an aspect of the graphic object 10 displayed on the display unit 151, for example, brightness, color, size, shape, etc. In other words, in a power saving mode, the controller 180 may display a graphic object corresponding to an application set to be in a background disabled state, and a graphics object corresponding to an application set to be in a state. activated in the background, to distinguish them visually, among graphic objects corresponding to applications included in a home screen page. More specifically, as shown in FIG. 8A, in a power saving mode, the controller 180 may display the graphics object 310 corresponding to an application set to be in a background disabled state together with a graphics object. 800 indicating notification information. The graphic object 800 indicating notification information may represent information regarding a disabled state in the background of an application. Alternatively, the controller 180 may display the graphic object 800 indicating notification information, overlapped with the graphic object 310 corresponding to the application set to be in a background disabled state. The controller 180 can not display the graphic object 300 corresponding to an application set to be in a background activated state, along with the graphic object 800 indicating notification information. That is, in one embodiment of the present invention, since a graphical object corresponding to an application set to be in a background disabled state is output together with notification information, a user may be informed the disabled state in the background of the application.
[0035] The display unit 151 may output the graphic object differently depending on a type of LED or type of LCD. More specifically, in the case of the LED type, the display unit 151 may output the graphic object by controlling a brightness of the graphic object. On the contrary, in the case of the LCD type, the display unit 151 can output the graphic object by controlling a color of the graphic object. The controller 180 may output a background enabled state and a background deactivated state of applications in a different manner, depending on an output type of the display unit 151. For example, as shown in FIG. 8B, if the display unit 151 adopts a type of LCD, the controller 180 can display the remaining applications except for an application set to be in a background activated state, in gray, in a power saving mode. In this case, the application set to be in a background enabled state may be displayed in a different color rather than the gray color, so as to visually distinguish it from the remaining applications set to be in a disabled state. background. As a further example, if the display unit 151 adopts a type of LED, the controller 180 can display the remaining applications except for an application set to be in a background activated state, in which a dark color, in an energy saving mode. In this case, the application set to be in a background enabled state can be displayed in bright color, while the remaining applications set to be in a background off state can be displayed in a dark color. The above description describes a method of displaying a running state in the background of an application on a home screen page. In one embodiment of the present invention, a user can intuitively recognize an application background state of an application on the home screen page. Hereinafter, a method of providing a home screen page in a power saving mode will be explained. Figs. 9A to 9E are conceptual views illustrating a method of providing a home screen page in a power saving mode. Once a power saving mode is executed, the mobile terminal can provide the same home screen page as in a general mode, as mentioned above. The same home screen page as a general mode 3037164 37 corresponds to a type of a graphic object included in a home screen page, and a type of display (size, color, position, etc. .) a graphic object is the same in a power saving mode and a general mode. As a further example, once a power saving mode 5 is executed, the mobile terminal can provide a home screen page having only a graphics object corresponding to an application set to be in an enabled state. background. For the sake of convenience, in one embodiment of the present invention, a home screen page having only a graphic object corresponding to an application set to be in a background enabled state is referred to as a page of the present invention. energy saving home screen. Once a power saving mode is executed, the controller 180 can set one of a plurality of home screen pages implemented in a general mode, as a home screen page. 'energy saving. Alternatively, the controller 180 may generate a new home screen page different from a plurality of home screen pages implemented in a general mode, as an economy home screen page. energy. That is, in one embodiment of the present invention, applications recommended for use in a power-saving mode may be provided at a time, when the energy-saving home screen page is provided. .
[0036] For example, as shown in a first drawing of Figure 9A, the controller 180 can provide three home screen pages in a general mode. Once a power saving mode is executed, the controller 180 can set one of the three home screen pages as a power saving home screen page. The energy saving home screen page may include thereon an application set to be in a background enabled state. For example, as shown in a second drawing of Figure 9A, the controller 180 can provide the first home screen page among the three home screen pages as a home screen page. 'energy saving. The energy saving home screen page may include thereon the graphic object 300 corresponding to the notes application set to be in a background activated state in a power save mode. . The controller 180 may display a graphic object corresponding to an application set to be in a background disabled state in a power save mode on the remaining home screen page. For example, as shown in a third drawing of FIG. 9A, the controller 180 can display the graphic object 310 corresponding to an SNS application set to be in a deactivated state in the background in a power saving mode, on the second page 5 home screen among the three home screen pages. As a further example, as shown in the first and second drawings of Fig. 9B, once a power saving mode is executed, the controller 180 can generate a new home screen page different from a plurality of home screen pages implemented in a general mode, as the 900 energy saving home screen page 900. The energy saving home screen page 900 may include thereon a graphic object corresponding to an application set to be in a background activated state in a power save mode, a remaining amount of power of a battery (910b), and a hold time power supply (910a) indicating a usable time of the mobile terminal based on the remaining amount of battery current. The controller 180 may further display a shortcut graphic object 200d corresponding to the energy saving home screen page 900. The shorthand graphic object 200d corresponding to the home screen page of Energy Saver 900 may have a different form of the remaining shortcut graphics objects 200a, 200b, 200c relating to home screen pages including applications set to be in a background disabled state. For example, as shown in a second drawing of Fig. 9B, the shorthand graphic object 200d can be displayed in quadrangular form, and the remaining shortcut graphic objects 200a, 200b, 200c can be displayed in a circular form.
[0037] With such a configuration, a user can distinguish the energy-saving home screen page 900 from the remaining home screen pages. The controller 180 can add or remove an application to be set to be in a background enabled state, on or from the power saving home screen page. In the case of adding a graphical object corresponding to an application on the energy saving home screen page, the controller 180 can set the graphic object to be in a state. activated in the background. For example, as shown in a first drawing of FIG. 9C, the energy saving home screen page may include thereon a graphic object indicating an application adding function. As shown in a second drawing of Fig. 9C, the controller 180 may display on the display unit 151, a list of applications 920 having a plurality of applications installed on the mobile terminal, based on a touch input. applied on the graphic object. The controller 180 can add at least one application to the energy saving home screen page, using the application list 920. For example, as shown in a second drawing of Fig. 9C, the controller 180 may select a gallery application for providing images, according to a selection of the user. Once the gallery application is selected, the controller 180 may display the gallery application on the energy-saving home screen page, and may adjust the gallery application to be in a state activated in the background. In contrast, as shown in the second and third drawings of FIG. 9D, the controller 180 can select the gallery application, not the notes application included in the energy-saving home screen page. , according to a selection of the user. In this case, the controller 180 may control the graphics object 300 corresponding to the notes application to disappear from the energy-saving home screen page, and may adjust the notes application for 20 it is in a disabled state in the background. The controller 180 may display a graphical object 350 relating to the gallery application on the energy saving home screen page, and may set the gallery application to be in an enabled state. background. That is, in one embodiment of the present invention, when an application is added to or deleted from a home screen page, an activation state in the background of the application can be determined. in a practical way. In addition, when deleting a graphic object corresponding to an application of the energy saving home screen page, the controller 180 can set the deleted application to be in a disabled state. background.
[0038] That is, in one embodiment of the present invention, when an application is added to or deleted from the power saving home screen page, a background enabled state or a disabled state. in the background of the application can be set. In addition, when a current mode of the mobile terminal 3037164 is converted to a general mode from a power saving mode, the controller 180 can no longer provide the energy saving home screen page. which has been supplied in the energy saving mode. For example, as shown in the first and second drawings of FIG. 9E, when a current mode of the mobile terminal is converted to a general mode from a power saving mode, the controller 180 can control the page of the energy-saving home screen so that it disappears from the display unit 151. In other words, the energy-saving home screen page can be a screen page of the screen. only temporarily supplied in the 10 energy saving mode. In this case, the controller 180 can unblock a disabled state in the background of an application that has been set to be in the disabled state in the background. In other words, if the application is running in the background in a general mode, the controller 180 can set the application to be in a background enabled state. The above description describes a method of providing a power saving home screen page in a power saving mode. In one embodiment of the present invention, applications recommended for use in an energy saving mode may be provided at a time via the energy saving home screen page. In addition, a user can quickly access the recommended applications for use in the power saving mode via the energy saving home screen page. Hereinafter, a method of executing applications in an energy saving mode will be explained. Figs. 10A to 10C are conceptual views illustrating a method of executing applications in a power saving mode.
[0039] The mobile terminal of the present invention can control the execution of a background application in a power save mode. In the same way as a general mode, the controller 180 of the mobile terminal can control all the applications installed on the mobile terminal, so that they are executed in the foreground in a power saving mode. In other words, in one embodiment of the present invention, in an energy saving mode, the execution of an application in the foreground is not restricted, but the execution of an application backwards plan can be controlled.
[0040] In a power-saving mode, the controller 180 may execute in the foreground a set of applications to be in a background enabled state, and a set of applications to be in the background. a disabled state in the background, in a different way. More specifically, if a request to execute the user of an application in the foreground is received, the controller 180 may execute the application that has been set to be in a background activated state, the same way as a general mode. That is, when the application set to be in a background enabled state is executed in the background, the controller 180 can immediately execute the application without loading the application from the memory 170. On the contrary, when the application set to be in a background enabled state is not running in the background (that is, if the application is in a background disabled state), the controller 180 can execute the application after loading the application from memory 170.
[0041] For example, as shown in a first drawing of Fig. 10A, when the notes application is set to be in a background enabled state, a short touch input can be applied to the graphic object 300 corresponding to the application notes, so that the notes application is run in the foreground. In this case, as shown in the second drawing of FIG. 10A, the controller 180 may execute the notes application in the manner mentioned above. Upon completion of the execution in the foreground of the application set to be in a background enabled state, the controller 180 may run the application in the background in an enabled state, or may disable the application in the background. 'application. On the contrary, if a request from the user of execution of an application in the foreground 25 is received, the controller 180 can execute in the foreground the application which has been set to be in a disabled state in the background. plan. In this case, the controller 180 may output notification information indicating that the application whose foreground execution has been requested has been set to be in a disabled state in the background, before executing. the application. The notification information may include information indicating that the application has been set to be in a background disabled state, and the application will be re-set to a background disabled state after it has been executed. foreground.
[0042] For example, as shown in a first drawing of Fig. 10B, the controller 180 can detect a short touch input applied to the graphic object 310 corresponding to an application set to be in a background disabled state, so that to run the application in the foreground. In this case, as shown in a second drawing of Fig. 10B, the controller 180 may output notification information, before running in the foreground the application set to be in a disabled state in the background. . In other words, in one embodiment of the present invention, when an application whose execution has been requested has been set to be in a disabled state in the background, a user can recognize that the application can be used. only when a feature related to the application is running in the foreground. The controller 180 may execute the set application to be in a background disabled state, in the same manner as an application set to be in a background enabled state. Upon completion of the execution of the application set to be in a background disabled state, the controller 180 may run the application in the background in a disabled state, or may disable the application. That is, as shown in FIG. 10B, upon completion of the foreground execution of the application set to be in a background off state, the controller 180 can reset the application to quit. it is in a disabled state in the background. That is, when the application set to be in a background disabled state is running in the background after it has been executed in the foreground, even if a request to execute a function related to the application is received from the application, the application-related function may not be executed. When a specific application is executed in a power saving mode, the controller 180 can adjust the remaining applications installed on the mobile terminal to be in a background disabled state. More specifically, when a specific application is run in the foreground in a power saving mode, the controller 180 can detect a current consumption amount of the specific application. For example, as shown in a first drawing of Fig. 10C, the controller 180 may execute a video playback application for playing videos (moving pictures) in a foreground mode in a power saving mode. The controller 180 can detect an amount of power consumed by the video playback application. If the amount of current detected per hour of the application running in the foreground is greater than a preset amount of current, the controller 180 may output notification information to adjust the remaining applications to be in a disabled state in the background. The preset current amount can be preset as a reference value, or can be adjusted based on a current remaining amount of a battery. For example, the preset amount of current can be preset to memory 170 as a specific value. Alternatively, the preset amount of current can be set as a calculated value by deducting 10% of a current remaining amount from a battery by the controller 180. The notification information may be information asking whether to adjust the remaining applications installed on the mobile terminal to be in a disabled state in the background, to a user. For example, as shown in a second drawing of Fig. 10C, while a video application is running in the foreground, the controller 180 may output notification information in the form of an intruder window, the notification information asking whether to fix the remaining applications installed on the mobile terminal 20 to be in a disabled state in the background, to a user. If a request to set all the applications installed on the mobile terminal to be in a disabled state in the background is received by the user, the controller 180 can adjust the remaining applications except the application. Specifically executed in the foreground, so that they are in a deactivated state in the background. Upon completion of executing the specific application in the foreground, the controller 180 can unblock a background disabled state of the remaining applications set to be in a background disabled state. In this case, an application running in the background may perform a function relating thereto because a background disabled state thereof has been unblocked. For example, a notes application may receive a message from an external server or an external terminal, via a network communication, when a background disabled state thereof has been unblocked.
[0043] As a further example, when a current consumption amount per hour of an application running in the foreground is greater than a preset value, the controller 180 can only set applications unrelated to the executed application. in the foreground, so that they are in a background disabled state, among a plurality of applications installed on the mobile terminal. Applications unrelated to the application running in the foreground may be applications that are not running with the application running in the foreground. For example, if the application running in the foreground is a video application, the application unrelated to the video application may be a message application. The controller 180 can not set applications related to the application running in the foreground, so that they are in a disabled state in the background. In this case, applications relating to the application running in the foreground can be set to be in a background enabled state. For example, if a video application is running in the foreground, the controller 180 can set a video editing application to be in a background enabled state. When an amount of current consumption per hour of the application running in the foreground is greater than a preset value, the controller 180 can set at least one application to be in a background disabled state, according to a type of update of a plurality of applications installed on the mobile terminal. The type of update can be a type for using network communication by applications. For example, the type of update may include a type for downloading a file to be installed by the applications, a type for receiving a message from an external server or an external terminal, etc. If the update type corresponds to a type for downloading a file to be installed by the applications, the controller 180 can set the applications to be in a disabled state in the background. If update type 30 corresponds to a type for receiving a message from an external server or external terminal, controller 180 can set applications to be in a background enabled state .
[0044] With such a configuration, in one embodiment of the present invention, when an application having a large amount of power consumption is executed, a standby current of the mobile terminal can be minimized. In addition, in the case of an application running in the background of the mobile terminal, the execution of a function relating to the application may be restricted in the background of the mobile terminal. Thus, in one embodiment of the present invention, the consumption of a standby current, due to the execution of a function relating to a background application, can be prevented without additional control control applied backwards. -plan.
[0045] Furthermore, in one embodiment of the present invention, since an application running in the background is continuously performed without being interrupted, the power consumption of a standby current can be reduced, and a user can quickly access the application. Further, in one embodiment of the present invention, when an application is running in the background, only the execution of a function relating to the application is restricted, without downloading the application from a memory. As a result, the power consumption of a standby current can be reduced, and a user can quickly access the application. Various embodiments may be implemented using a machine-readable medium on which instructions for execution by a processor are stored to perform various methods presented herein. Examples of possible machine readable media include a hard disk drive (HDD), a solid state disk (SSD), a silicon disk drive (SDD), a read only memory, a RAM, a CD-ROM , a magnetic tape, a floppy disk, an optical data storage device, the other types of storage media presented herein, and combinations thereof. If desired, the machine-readable medium may be embodied as a carrier wave (e.g., transmission over the Internet). The processor may include the controller 180 of the mobile terminal.
[0046] The foregoing embodiments and advantages are provided solely by way of example and should not be construed as limiting the present disclosure. The present teachings can be easily applied to other types of apparatus. This description is intended to be illustrative, and not to limit the scope of the claims. Many variations, modifications and variations will be apparent to those skilled in the art. The features, structures, methods, and other features of the exemplary embodiments described herein may be combined in various ways to provide examples of additional and / or alternative embodiments. Since the present features may be incorporated in various forms without departing from their characteristics, it is also to be understood that the embodiments described above are not limited by any of the details of the foregoing description unless otherwise specified, but must be rather be considered in a general sense within its scope as defined in the appended claims, and therefore any changes and modifications which fall within the scope of the claims, or equivalents thereof, are therefore intended to be understood by the appended claims.

权利要求:
Claims (15)
[0001]
REVENDICATIONS1. A mobile terminal, comprising: a display unit (151) configured to display a home screen page having graphic objects corresponding to applications installed on the mobile terminal; and a controller (180) configured to: execute a corresponding application in a background, control the corresponding application to be in a background enabled state or a background disabled state in response to a pre-set type of tactile input applied to a graphic object of the corresponding application, when the corresponding application is in the deactivated state in the background, when receiving a request generated by the corresponding application for executing the application. a function relating to the corresponding application, not executing the function relating to the corresponding application, and when the corresponding application is in the activated state in the background, when the request generated by the application is received. corresponding application for executing the function relating to the corresponding application, executing the function relating to the corresponding application.
[0002]
The mobile terminal of claim 1, wherein when the function relating to the corresponding application is not executed, the controller (180) is further configured to transmit, to the corresponding application, a feedback signal indicating that the request was refused.
[0003]
The mobile terminal of claim 1 to 2, wherein the controller (180) is further configured to display graphic objects on the display unit (151) corresponding to applications in the backward activated state. plan so that they can be visually distinguished from graphical objects corresponding to applications in the disabled state in the background. 30
[0004]
The mobile terminal of claim 1 to 3, wherein the controller (180) is further configured to: enter the mobile terminal in a power saving mode in response to a request from the user, and adjust the corresponding application to be in the background enabled state or the background disabled state in the power save mode. 5
[0005]
The mobile terminal of claim 1 to 4, wherein the controller (180) is further configured to display an added splash screen page on the display unit (151) comprising only graphics objects corresponding to applications in the activated state in the background. 10
[0006]
The mobile terminal of claim 1 to 5, wherein the controller (180) is further configured to convert the activated state in the background of the corresponding application to the disabled state in the background, according to a pre-set type of touch applied to the graphic object of the corresponding application.
[0007]
The mobile terminal of claim 1 to 5, wherein the controller (180) is further configured to set the background enabled state or the background disabled state of the applications, according to a schema. use of applications.
[0008]
The mobile terminal of claim 1 to 5, wherein when the corresponding application is executed in the foreground, the controller (180) is further configured to tune remaining applications to be in the disabled state. background.
[0009]
The mobile terminal of claim 8, wherein when the corresponding application running in the foreground satisfies a preset condition, the controller (180) is further configured to display an intruder window asking whether to adjust the remaining applications for they are in the off state in the background on the display unit (151).
[0010]
The mobile terminal of claim 8, wherein upon completion of executing the corresponding application in the foreground, the controller (180) is further configured to unblock the disabled state backward. map of the remaining applications.
[0011]
The mobile terminal of claim 1 to 5, wherein the corresponding application is loaded into a RAM of the mobile terminal in the deactivated state in the background and the state activated in the background.
[0012]
Mobile terminal according to claim 1 to 5, wherein when the corresponding application is in the deactivated state in the background, and upon receipt of a request for execution of the corresponding application in advance. In the plan, the controller (180) is further configured to directly convert the disabled state in the background of the corresponding application into a foreground enabled state.
[0013]
The mobile terminal of claim 12, wherein the controller (180) is further configured to control the corresponding application to be in the enabled state only when the application is running in the foreground.
[0014]
The mobile terminal of claim 12, wherein when the corresponding application is interrupted in the activated state, the controller (180) is further configured to control the corresponding application to go to the state. disabled in the background of the activated state.
[0015]
15. Method of controlling a mobile terminal, the method comprising: displaying, via a display unit (151), a home screen page 25 comprising graphic objects corresponding to applications installed on the mobile terminal; executing, via a controller (180), a corresponding application in a background; controlling, through the controller (180), the corresponding application to be in a background enabled state or a background disabled state, responsive to a pre-set type of touch input applied to a graphic object of the corresponding application; 3037164 50 when the corresponding application is in the deactivated state in the background, when receiving a request generated by the corresponding application for execution of a function relating to the corresponding application, the non-execution, via the controller (180), the function relating to the corresponding application; and when the corresponding application is in the background activated state, upon receipt of the request generated by the corresponding application for execution of the function relating to the corresponding application, the execution via the controller (180), of the function relating to the corresponding application.

类似技术:

---

公开号 | 公开日 | 专利标题

---

FR3037164B1|2019-06-21|MOBILE TERMINAL AND METHOD OF CONTROLLING THE SAME

---

JP6533174B2|2019-06-19|Locked camera access

---

RU2636137C2|2017-11-20|Method and device for installing working condition of intelligent home device

---

US20170205894A1|2017-07-20|Method and device for switching tasks

---

US9058128B1|2015-06-16|Power management for electronic devices

---

US20150333971A1|2015-11-19|Method and device for managing processes of application program

---

US10474507B2|2019-11-12|Terminal application process management method and apparatus

---

US20160026534A1|2016-01-28|Method and device for saving storage space

---

KR102247817B1|2021-05-04|Method and apparatus for providing lockscreen

---

KR20120064096A|2012-06-18|Methods and systems for operating a computer via a low power adjunct processor

---

FR3040221A1|2017-02-24|

---

US8577971B2|2013-11-05|Email fetching system and method in a portable electronic device

---

US20150100813A1|2015-04-09|Method and device for processing images to save power

---

KR20130142642A|2013-12-30|Mobile terminal, server, system, method for controlling of the same

---

US20160018984A1|2016-01-21|Method of activating user interface and electronic device supporting the same

---

US20200401419A1|2020-12-24|Method for Managing Application Program Use Time Offline, and Terminal Device

---

US10311254B2|2019-06-04|Electronic apparatus and information access control method thereof

---

WO2016150104A1|2016-09-29|App theme loading method and device

---

US10592534B2|2020-03-17|Automated aggregation of social contact groups

---

US10356188B2|2019-07-16|Dynamic update of tips on a device

---

US9781198B2|2017-10-03|Information processing method and electronic device

---

US20150286361A1|2015-10-08|Single gesture video capture and share

---

WO2015078286A1|2015-06-04|Method and device for managing spam message

---

US20200293583A1|2020-09-17|Information search method, terminal, network device, and system

---

US11245786B2|2022-02-08|Recommendation method and terminal

同族专利:

---

公开号 | 公开日

---

US20160357394A1|2016-12-08|

---

EP3101958B1|2019-11-06|

---

CN106249841A|2016-12-21|

---

FR3037164B1|2019-06-21|

---

EP3101958A1|2016-12-07|

---

KR20160143429A|2016-12-14|

引用文献:

---

公开号 | 申请日 | 公开日 | 申请人 | 专利标题

---

---

CN101692195A|2009-09-29|2010-04-07|聂清永|Method for displaying and controlling control menu on touch screen|

---

US8244311B2|2009-12-29|2012-08-14|International Business Machines Corporation|Time-related power systems|

---

US20120209413A1|2011-02-14|2012-08-16|Microsoft Corporation|Background Audio on Mobile Devices|

---

US8886976B2|2011-04-11|2014-11-11|Microsoft Corporation|Management of background tasks|

---

US8997171B2|2011-08-19|2015-03-31|Microsoft Technology Licensing, Llc|Policy based application suspension and termination|

---

WO2012149738A1|2011-09-14|2012-11-08|华为技术有限公司|Power management method and device for mobile terminal|

---

KR102070276B1|2012-04-24|2020-01-28|엘지전자 주식회사|Mobile terminal and control method for the mobile terminal|

---

EP3296868A1|2012-06-06|2018-03-21|Huawei Device Co., Ltd.|Application management method and terminal|

---

US8971870B2|2012-08-10|2015-03-03|Kyocera Corporation|Mobile terminal device, and control method for mobile terminal device|

---

CN102799261B|2012-08-30|2016-02-10|天津英利新能源有限公司|A kind of method and device realizing screen protection|

---

US9489236B2|2012-10-31|2016-11-08|Microsoft Technology Licensing, Llc|Application prioritization|

---

KR102013940B1|2012-12-24|2019-10-21|삼성전자주식회사|Method for managing security for applications and an electronic device thereof|

---

JP6016670B2|2013-02-26|2016-10-26|シャープ株式会社|Mobile terminal device|

---

US20140293848A1|2013-03-28|2014-10-02|Alcatel-Lucent Usa Inc.|Communication device data channel access|

---

CN103412708B|2013-07-31|2016-12-28|华为技术有限公司|Task management method on terminal unit and terminal unit|

---

KR102131826B1|2013-11-21|2020-07-09|엘지전자 주식회사|Mobile terminal and controlling method thereof|KR20170098106A|2016-02-19|2017-08-29|삼성전자주식회사|Configuration setting method and device|

---

US20180063670A1|2016-08-26|2018-03-01|Microsoft Technology Licensing, Llc|Background management of mobile applications|

---

CN106843445A|2016-12-30|2017-06-13|刘超|The method and mobile terminal of a kind of power saving|

---

KR20190051723A|2017-11-07|2019-05-15|삼성전자주식회사|Method for providing mode switching, electronic apparatus and storage medium|

---

US10375313B1|2018-05-07|2019-08-06|Apple Inc.|Creative camera|

---

CN110858302A|2018-08-24|2020-03-03|英业达科技有限公司|System and method for editing monitoring script in picture image|

---

US11107261B2|2019-01-18|2021-08-31|Apple Inc.|Virtual avatar animation based on facial feature movement|

---

US11131967B2|2019-05-06|2021-09-28|Apple Inc.|Clock faces for an electronic device|

法律状态:
2017-05-30| PLFP| Fee payment|Year of fee payment: 2 |

---

2018-05-11| PLSC| Publication of the preliminary search report|Effective date: 20180511 |

---

2018-05-29| PLFP| Fee payment|Year of fee payment: 3 |

---

2019-03-27| PLFP| Fee payment|Year of fee payment: 4 |

---

2020-04-08| PLFP| Fee payment|Year of fee payment: 5 |

---

2022-02-11| ST| Notification of lapse|Effective date: 20220105 |

优先权:

---

申请号 | 申请日 | 专利标题

---

KR1020150080143A|KR20160143429A|2015-06-05|2015-06-05|Mobile terminal and method for controlling the same|

---

KR1020150080143|2015-06-05|

---